Business rules for configurable metamodels and enterprise impact analysis

ABSTRACT

A metadata management system for importing, integrating and federating metadata, including a configurable metamodel, a metadata repository for storing metadata whose structure reflects the metamodel, at least one external metadata source, which is able to persist metadata in accordance with the structure of a meta-schema, a mapping module for mapping the meta-schema to the metamodel, and a transformation module, operatively coupled to the metadata mapping module, for translating specific metadata from the at least one external metadata source to the metadata repository, for use in import, export or synchronization of metadata between the external metadata source and the metadata repository. A method and a computer-readable storage medium are also described.

CROSS REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of assignee's pendingapplication U.S. Ser. No. 10/053,045, filed on Jan. 15, 2002, entitled“Method and System for Deriving a Transformation by Referring Schema toan Central Model,” which is a continuation-in-part of assignee's pendingapplication U.S. Ser. No. 09/866,101, filed on May 25, 2001, entitled“Method and System for Collaborative Ontology Modeling.”

FIELD OF THE INVENTION

The present invention relates to management of enterprise metadata.

BACKGROUND OF THE INVENTION

Large enterprises rely on vast amounts and diverse types of data fortheir operation—personnel data, financial data, accounting data,inventory data, capital equipment data, document management data, andmore. Today, data is generally stored according to data structuresreferred to as a data schemas, such as XML and relational databaseschemas, these being a form of metadata. The term “metadata” is used todenote data about the structure of the raw data itself, and about thestructures of other Information Technology (IT) systems such asapplications, processes, middleware and hardware configurations. The rawdata, which includes actual data about specific personnel, for example,or specific pieces of inventory, is referred to as “instance data.”Thus, for a data store having the structure of a relational database,the metadata describes the tables and their columns to be populated withdata, and the raw data, referred to as instance data, is the actual datastored within the tables and columns. Similarly, for a data store of XMLdocuments, the metadata describes the XML complexTypes and their XMLelements, and the instance data is the actual data stored within the XMLdocuments. Each data store is referred to generically as a “data asset.”

Types of metadata include inter alia data schemas such as relational andXML schemas, source code, architecture models such as information modelsand process models, operational metadata regarding usage of applicationsand up-time, hardware inventories and configurations, service levelagreements, and IT budgets.

It is common for large enterprises to have thousands of different dataassets, each with a unique schema; i.e., thousands of different metadatadescriptions, within their IT. For example, financial data may be spreadout over several different relational databases, personnel data may bespread out over several different XML document stores, and inventorydata may be spread out according to several different Cobol Copybookdefinitions.

In order to describe all of the different types of enterprise IT assets,including inter alia data assets and applications, a metamodel is usedto model the entire repertoire of IT asset types. Such asset typesinclude inter alia relational database schemas, XML schemas, COBOLCopybook definitions, Java applications, Engage Transform and Load (ETL)middleware and the structures associated therewith. A “metamodel” is amodel for metadata, and describes the types of assets within theenterprise IT, and their inter-dependencies. Actual metadata itselfinstantiates the metamodel.

The three levels of data—instance data, metadata and metamodel, form adata hierarchy, wherein the structure of each level of data is describedby the level above it. The three data levels within the data hierarchyare denoted by M0 (instance data), M1 (metadata) and M2 (metamodel).More generally, M0 includes instance data, messages and specificinteractions; M1 defines actual IT structures, such as specific schemas,interfaces and inter-dependencies; and M2 describes types of structuresand cross-references of IT.

In order to enable efficient use of a rich and configurable metamodel, asystem is needed that supports (i) metamodel editing; (ii) classes,properties, inheritance and multiple inheritance within a metamodel; and(iii) industry standards such as Meta-Object Facility (MOF™) forstructure of the metamodel, XML Interchange (XMI™) for import and exportof metadata, and standard metamodels such as the Common WarehouseMetamodel (CWM™) and the DMTF Common Information Model (CIM™). MOF™, XMIand CWM™ are standards developed by the Object Modeling Group (OMG®);and CIM is a standard developed by Distributed Management Task Force,Inc. (DMTF™).

While the prior art includes flexible metamodels such as MOF-compliantmetamodels, which flexibly define the structure of metadata, metamodelshave not been used to describe specific rules which metadata must obey.Therefore, metamodels have hitherto had limited use in the detailedgovernance of IT.

Furthermore, although there are standard languages such as MOF forspecifying metamodels, in reality sources of metadata currently havetheir own metamodels, making it difficult to accumulate metadata fromdifferent sources into one overall metadata model of enterprise IT.

SUMMARY OF THE DESCRIPTION

The present invention concerns a method and system for metadatamanagement. The present invention supports (i) a rich and configurablemetamodel with run-time metamodel editing; (ii) multiple inheritance andthe addition of business rules within a metamodel; (iii) industrystandards such as MOF™, XMI™, CWM™ and CIM™. The metamodel of thepresent invention supports an endless number of types of metadata,including inter alia metadata for data assets, business applications,organization charts, process models, hardware configurations and networktopographies; and (iv) mapping between incompatible metamodels to enableimport, export, synchronization and federation of metadata.

There is thus provided in accordance with a preferred embodiment of thepresent invention a metadata management system for importing,integrating and federating meta-data, including a configurable metamodelfor modeling metadata that describes enterprise IT assets, a metadatarepository for storing metadata whose structure reflects the metamodel,at least one external metadata source, which is able to persist metadatain accordance with the structure of a meta-schema, a mapping module formapping the meta-schema to the metamodel, and a transformation module,operatively coupled to the metadata mapping module, for translatingspecific metadata from the external metadata source to the metadatarepository, for use in import, export or synchronization of metadatabetween the at least one external metadata source and the metadatarepository.

There is further provided in accordance with a preferred embodiment ofthe present invention a metadata management system for validatingmetadata, including a configurable metamodel for modeling metadata thatdescribes enterprise IT assets, business rules on the metamodel, and ametadata validation module operating on said configurable metamodel forvalidating specific metadata against the metamodel business rules.

There is yet further provided in accordance with a preferred embodimentof the present invention a metadata management system for generatingmetadata including a configurable metamodel for modeling metadata thatdescribes enterprise IT assets, business rules on the metamodel, and ametadata generation module operating on said configurable metamodel forguiding the generation of specific metadata using the metamodel businessrules.

There is moreover provided in accordance with a preferred embodiment ofthe present invention a metadata management system for managing an ITorganization, including a configurable metamodel for modeling metadatathat describes enterprise IT assets, business rules on the metamodel,and a validation module operating on said configurable metamodel forvalidating rules for IT governance against the metamodel business rules.

There is additionally provided in accordance with a preferred embodimentof the present invention a method for importing, integrating andfederating metadata, including providing (i) a configurable metamodelfor modeling metadata that describes enterprise IT assets, (ii) ametadata repository for storing metadata whose structure reflects themetamodel, and (iii) at least one external metadata source, which isable to persist metadata in accordance with the structure of ameta-schema, mapping the meta-schema to the metamodel, and translatingspecific metadata from the at least one external metadata source to themetadata repository for use in import, export or synchronization ofmetadata between the external metadata source and the metadatarepository.

There is further provided in accordance with a preferred embodiment ofthe present invention a method for validating metadata, includingproviding (i) a configurable metamodel for modeling metadata thatdescribes enterprise IT assets, and (ii) business rules on themetamodel, and validating specific metadata against the metamodelbusiness rules.

There is yet further provided in accordance with a preferred embodimentof the present invention a method for generating metadata includingproviding (i) a configurable metamodel for modeling metadata thatdescribes enterprise IT assets, and (ii) business rules on themetamodel, and guiding the generation of specific metadata using themetamodel business rules.

There is moreover provided in accordance with a preferred embodiment ofthe present invention a method for managing an IT organization,including providing (i) a configurable metamodel for modeling metadatathat describes enterprise IT assets, and (ii) business rules on themetamodel, and validating rules for IT governance against the metamodelbusiness rules.

There is additionally provided in accordance with a preferred embodimentof the present invention a computer-readable storage medium storingprogram code for causing a computer to perform the steps of providing(i) a configurable metamodel for modeling metadata that describesenterprise IT assets, (ii) a metadata repository for storing metadatawhose structure reflects the metamodel, and (iii) at least one externalmetadata source, which is able to persist metadata in accordance withthe structure of a meta-schema, mapping the meta-schema to themetamodel, and translating specific metadata from the at least oneexternal metadata source to the metadata repository for use in import,export or synchronization of metadata between the external metadatasource and the metadata repository.

There is further provided in accordance with a preferred embodiment ofthe present invention a computer-readable storage medium storing programcode for causing a computer to perform the steps of providing (i) aconfigurable metamodel for modeling metadata that describes enterpriseIT assets, and (ii) business rules on the metamodel, and validatingspecific metadata against the metamodel business rules.

There is yet further provided in accordance with a preferred embodimentof the present invention a computer-readable storage medium storingprogram code for causing a computer to perform the steps of providing(i) a configurable metamodel for modeling metadata that describesenterprise IT assets, and (ii) business rules on the metamodel, andguiding the generation of specific metadata using the metamodel businessrules.

There is moreover provided in accordance with a preferred embodiment ofthe present invention a computer-readable storage medium storing programcode for causing a computer to perform the steps of providing (i) aconfigurable metamodel for modeling metadata that describes enterpriseIT assets, and (ii) business rules on the metamodel, and validatingresponsibility assignments against the metamodel business rules.

There is additionally provided in accordance with a preferred embodimentof the present invention a metadata management system for performingimpact analysis on an IT system comprising a configurable metamodel formodeling metadata that describes assets of an enterprise IT system, themetamodel including meta-classes and meta-properties, business rules onthe metamodel for indicating that certain meta-properties have impactconsequences, and an impact analyzer operating on the configurablemetamodel for determining which assets of the enterprise IT system areimpacted by one or more specified assets.

There is further provided in accordance with a preferred embodiment ofthe present invention A method for generating metadata comprisingproviding (i) a configurable metamodel for modeling metadata thatdescribes assets of an enterprise IT system, the metamodel includingmeta-classes and meta-properties, and (ii) business rules on saidmetamodel for indicating that certain meta-properties have impactconsequences, and determining which assets of the enterprise IT systemare impacted by one or more specified assets.

There is yet further provided in accordance with a preferred embodimentof the present invention a computer-readable storage medium storingprogram code for causing a computer to perform the steps of providing(i) a configurable metamodel for modeling metadata that describes assetsof an enterprise IT system, the metamodel including meta-classes andmeta-properties, and (ii) business rules on said metamodel forindicating that certain meta-properties have impact consequences, anddetermining which assets of the enterprise IT system are impacted by oneor more specified assets.

There is moreover provided in accordance with a preferred embodiment ofthe present invention a metadata management system for performing impactanalysis on an IT system including a configurable metamodel for modelingmetadata that describes assets of an enterprise IT system, the metamodelincluding meta-classes and meta-properties, a meta-descriptor formeta-properties to designate that a meta-property has an impactconsequence, and an impact analyzer operating on said configurablemetamodel for determining which assets of the enterprise IT system areimpacted by one or more specified assets.

There is additionally provided in accordance with a preferred embodimentof the present invention a method for generating metadata includingproviding (i) a configurable metamodel for modeling metadata thatdescribes assets of an enterprise IT system, the metamodel includingmeta-classes and meta-properties, and (ii) a meta-descriptor formeta-properties to designate that a meta-property has an impactconsequence, and determining which assets of the enterprise IT systemare impacted by one or more specified assets.

There is further provided in accordance with a preferred embodiment ofthe present invention a computer-readable storage medium storing programcode for causing a computer to perform the steps of providing (i) aconfigurable metamodel for modeling metadata that describes assets of anenterprise IT system, the metamodel including meta-classes andmeta-properties, and (ii) a meta-descriptor for meta-properties todesignate that a meta-property has an impact consequence, anddetermining which assets of the enterprise IT system are impacted by oneor more specified assets.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more fully understood and appreciated fromthe following detailed description, taken in conjunction with thedrawings in which:

FIG. 1 is a simplified illustration of an Object Management Grouphierarchy including instance data, metadata and a metamodel, inaccordance with a preferred embodiment of the present invention;

FIG. 2 illustrates a metamodel wherein a meta-class RDBSchema isassociated with a databaseAdministrator of type Person, in accordancewith a preferred embodiment of the present invention;

FIG. 3 illustrates a business rule requiring that every relationaldatabase must have a database Administrator, in accordance with apreferred embodiment of the present invention;

FIG. 4 illustrates a business rule wherein the name of a Cobol Copybookdefinition may be generated based on a naming standard from othermeta-properties of a Cobol Copybook, such as ApplicationName,DivisionName, in accordance with a preferred embodiment of the presentinvention;

FIG. 5 is a simplified block diagram of a metadata management system forimporting metadata, in accordance with a preferred embodiment of thepresent invention;

FIG. 6 is a simplified block diagram of a system for validatingmetadata, in accordance with a preferred embodiment of the presentinvention; and

FIG. 7 is a simplified block diagram of a system for automaticallyguiding the generation of metadata so as to ensure that the metadata iscompliant with business rules of a metamodel, in accordance with apreferred embodiment of the present invention;

FIG. 8 is an illustration of a dialogue box for creating an impactanalysis (IA) meta-class, in accordance with a preferred embodiment ofthe present invention;

FIG. 9 is an illustration of a dialogue box that continues the workflowfrom FIG. 8, for designating properties as being germane to a particularimpact analysis, in accordance with a preferred embodiment of thepresent invention;

FIG. 10 is an illustration of stepwise graphical navigation of ameta-model, in accordance with a preferred embodiment of the presentinvention;

FIG. 11 is an illustration of a graphic display of the transitiveclosure of impacted notes, in accordance with a preferred embodiment ofthe present invention;

FIG. 12 is an illustration of a graphical user interface for viewingdata lineage results arranged along a “data flow axis” and a “systemcomposition axis”, in accordance with a preferred embodiment of thepresent invention; and

FIG. 13 is an illustration of a graphical user interface for markingmeta-properties as being Downstream Items, Upstream Items, subunits orsuperUnits, in accordance with a preferred embodiment of the presentinvention.

DETAILED DESCRIPTION

The present invention is preferably embodied within at least one servercomputer used to store configurable information about enterprise dataassets in the form of a metamodel and metadata conforming to themetamodel; and within a plurality of client computers used to generateand edit metadata, and to query the metadata. The present inventionenables an enterprise to understand the structure of all of its dataassets and other IT assets, even when metadata information on thestructures comes from many sources in different formats. The presentinvention uses rules to impose restrictions on allowed metadata valuesand hence on the types of structures which may appear in the ITenvironment.

Reference is now made to FIG. 1, which is a simplified illustration ofan Object Management Group hierarchy including instance data, metadataand a metamodel, in accordance with a preferred embodiment of thepresent invention. A metamodel, referred to as an M2, is used to definethe structural elements of a data schema. For example, the M2illustrated in FIG. 1 describes the elements of a relational databaseschema. As shown, a relational database schema 105 includes elements 110referred to as “tables,” and in turn tables includes elements 115referred to as “columns.” A relational database 105, a table 110 and acolumn 115 each have a text identifier referred to as its “name.”

Metadata for a data schema, referred to as an M1, is used to define aspecific data schema conforming to the metamodel. As shown in FIG. 1,the M1 metadata specifies a relational database 120 named “CustomerDatabase.” The customer database has a table 125 named “Address” and atable 130 named “State.” In turn the Address table has a column 135named “Street Line” and a column 140 named “Zip Code;” and the Statetable has a column 145 named “Postal Code” and a column 150 named“Name.”

Specific instance data 155 conforming to the Customer Database, referredto as M0, is illustrated at the bottom of the hierarchy of FIG. 1. Itmay be appreciated that, just as M0 corresponds to instance data for anM1, in the same manner M1 corresponds to instance data for an M2.

Metamodels and metadata may be specified using the Meta-Object Facility(MOF™) specification, developed by Object Management Group, Inc. (OMG®)of Needham, Mass.

Preferably, in accordance with a preferred embodiment of the presentinvention, metamodels are represented in terms of an ontology havingclasses and properties, such as ontologies based on the W3C Web OntologyLanguage (OWL) standard, as described in applicant's co-pendingapplication U.S. Ser. No. 10/053,045, filed on Jan. 15, 2002, entitled“Method and System for Deriving a Transformation by Referring Schema toan Central Model,” the contents of which are hereby incorporated byreference. In order to distinguish between M1 metadata and M2metamodels, classes and properties within an M2 metamodel are referredto herein as meta-classes and meta-properties, respectively. In workingwith metamodels, it is often useful to consider meta-classes andmeta-properties as being class types and property types, respectively.For example, specific relational database tables such as Address andState are of type Table; i.e., they are instance classes of a meta-classTable.

Preferably, metamodel M2 includes business rules, which relate variousmeta-properties. Examples of such business rules are describedhereinbelow with reference to FIGS. 3 and 4.

Reference is now made to FIG. 2, which illustrates a metamodel wherein ameta-class RDBSchema 210 is associated with a databaseAdministrator 220of type Person 230, in accordance with a preferred embodiment of thepresent invention.

Reference is now made to FIG. 3, which illustrates a business rulerequiring that every relational database 310 must have a meta-propertydatabaseAdministrator 320 of type Person 330, in accordance with apreferred embodiment of the present invention. The business rule is setin FIG. 3 by marking the meta-property as Required 340. The cardinality250 of meta-property databaseAdministrator is [1 . . . 1], indicatingthat the minimum 350 and maximum 360 number of databaseAdministratorsper RDBSchema is 1.

Referring back to FIG. 2, an integrity checker 240 preferably lists allviolations of business rules. Thus, if a databaseAdministrator is notdefined for an RDBSchema, then integrity checker 240 will flag this as aviolation of the business rule shown in FIG. 3.

Reference is now made to FIG. 4, which illustrates a business rulewherein the name of a Cobol Copybook definition may be generated basedon a naming standard from other meta-properties of a Cobol Copybook,such as ApplicationName and DivisionName, in accordance with a preferredembodiment of the present invention. Specifically, business rule 410shown in FIG. 4 requires that the meta-property name 420 for themeta-class CobolCopybook 430 be the concatenation of the three stringsApplicationName 440, DivisionName 450 andFirstDataArchitectAssignedtothisAsset 460.

It may be appreciated by those skilled in the art that business rule 410may be used to automatically generate the name for a CobolCopybook.

Examples of business rules that may be used with the present inventioninclude inter alia:

-   -   arithmetic conversion rules;    -   type restrictions on inherited properties;    -   specifying metadata values as being required;    -   specifying valid ranges for metadata values;    -   specifying metadata values as being unique;    -   lookup tables;    -   naming conventions; and    -   assignments of stewardship responsibilities.

Business rules may also be used, in accordance with a preferredembodiment of the present invention, for type restrictions on indirectproperties. Consider the following indirect sequence of meta-classes andmeta-properties: C1.P1-->C2.P2-->C3. Suppose that the indirectmeta-property C1.P1.P2 should be restricted to be of type S3, which is asub-class of C3, but that C2.P2 is not to be restricted to S3. Ingeneral, there may not be an appropriate inheritance structure to imposesuch a restriction as a type restriction on an inherited property.

In accordance with a preferred embodiment of the present invention, anew meta-class, S2, corresponding to C1.P1, is defined as a sub-class ofC2, and a business rule is used to restrict the type of S2.P2 to S3.Using this approach, none of the properties P1 or P2 in the propertypath are required to be inherited properties. Moreover, this approachapplies to arbitrarily long property paths.

It may be appreciated by those skilled in the art that the presentinvention has widespread application. FIGS. 5-7 illustrate threedifferent applications of the present invention in the area ofenterprise metadata management.

Reference is now made to FIG. 5, which is a simplified block diagram ofa metadata management system for importing metadata, in accordance witha preferred embodiment of the present invention. FIG. 5 illustrates ametamodel of an enterprise, such as the metamodel illustrated in FIGS. 2and 4, including meta-classes and sub-classes for business applicationsand data assets. The class DataAsset includes inter alia sub-classesCobolCopybook, ErwinSchema, RDBSchema, XMISchema and XSDSchema. FIG. 2displays meta-properties for the RDBSchema meta-class, and FIG. 4displays metadata for the CobolCopybook meta-class.

Shown in FIG. 5 are a configurable metamodel 510, and a repository 520of metadata that conforms to metamodel 510. Also shown in FIG. 5 are anexternal meta-schema 530 and a repository 540 of metadata that conformsto meta-schema 530. Since the metadata in repository 540 conforms to adifferent meta-schema than the metadata in repository 520, the metadatain repository 540 cannot readily be imported into repository 520. Forexample, the metadata in repository 540 may be metadata for XML schemas,whereas the metadata in repository 520 may be metadata for relationaldatabase schemas.

The system illustrated in FIG. 5 imports the metadata from repository540 into repository 520. A mapping module 550 is used to generate amapping 560 between the meta-schema 530 and the metamodel 510.Generation of mappings between schemas is described in applicant'saforementioned co-pending patent application U.S. Ser. No. 10/053,045.For example, mapping 560 may associate XML Schema Metamodel XMLcomplexType --> class XML element --> property

When mapping 560 is generated, a metadata transformation module 570 usesmapping 560 to derive a data transformation for transforming metadatafrom repository 540 to metadata that conforms to metamodel 510. Upontransformation, the metadata in repository 540 can then be directlyimported into repository 520. Derivation of transformations is alsodescribed in applicant's aforementioned co-pending patent applicationU.S. Ser. No. 10/053,045.

For example, if metadata from repositories 520 and 540 is represented byXML data, which may conform to the Metadata Interchange (XMI) standard,then the data transformation derived by transformation module 570 may bean XSLT script. XMI is a standard of the Object Management Group (OMG®)for interchanging metadata between modeling tools and metadatarepositories, and XSLT is a language developed by the World-Wide WebConsortium (W3C®), for transforming XML documents into other XMLdocuments.

It may be appreciated by those skilled in the art that M1 metadata canbe considered as instance data for an M2 metamodel. As such the samemapping module 550 and the same transformation module 570 from FIG. 5,may also be used to map a first set of M1 metadata to a second set of M1metadata, and to transform M0 instance data conforming to the first setof metadata to M0 instance data conforming to the second set ofmetadata. This allows the same tools and skills to be used for mappingmetadata and transforming instance data, as is used for mappingmetamodels/meta-schemas and transforming metadata.

Reference is now made to FIG. 6, which is a simplified block diagram ofa system for validating metadata, in accordance with a preferredembodiment of the present invention. Shown in FIG. 6 are a configurablemetamodel 610 and a repository 620 of metadata conforming to metamodel610. Metamodel 610 includes one or more business rules 630, that relatemeta-properties within metamodel 610, such as the business rulesillustrated in FIGS. 3 and 4.

Shown in FIG. 6 is a validation module 640, which is preferablyactivated by a integrity checker control such as button 240 (FIG. 2).Preferably, validation module 640 verifies each of the business rules630 against the metadata in repository 620, and produces a list ofviolations. It may be appreciated that violations of metadata rules maycorrespond to violations of IT policy by the actual systems that themetadata reflects.

It may be appreciated that the system of FIG. 6 applies to a variety ofenterprise metadata. For example, metadata repository 620 may bemetadata for an IT organization, and the business rules may define validresponsibility assignments. In such a case, validation module 640 isused to validate responsibility assignments.

Reference is now made to FIG. 7, which is a simplified block diagram ofa system for automatically guiding the generation of metadata so as toensure that the metadata is compliant with business rules of ametamodel, in accordance with a preferred embodiment of the presentinvention. Alternatively, the generation of metadata may be motivated bythe desire to reduce the manual effort required in populating themetadata. Shown in FIG. 7 are a metamodel 710 and a repository 720 ofmetadata conforming to metamodel 720. Metamodel 710 includes one or morebusiness rules 730.

Also shown in FIG. 7 is a metadata guide 740, which automatically guidesa user who is generating metadata, so that the metadata complies withbusiness rules 730. For example, with reference to FIG. 2, metadataguide 740 automatically ensures that each RDBSchema has adatabaseAdministrator defined. Similarly, with reference to FIG. 4,metadata guide 740 automatically generates names of Cobol Copybooks, sothat the name of a Copybook is a concatenation of an ApplicationName, aDivisionName and a FirstDataArchitectAssignedtothisAsset name.

Impact Analysis

The present invention has important application to impact analysis;namely, analyzing the impact of one or more IT assets on the rest of theIT infrastructure—i.e., determining, if one or more IT assets are shutdown or modified, which other assets are impacted and how. Impactanalysis is critical for routine system maintenance, system upgrade ormodification, and for disaster recovery. Examples of impact analysisinclude inter alia:

-   -   determining which applications and systems will be impacted is a        specific server shuts down;    -   determining who needs to be notified if a computer is replaced        with a newer model;    -   determining which applications and systems will be impacted if a        specific employee is promoted;    -   determining which data sources are fed by data from a specific        database, either directly or indirectly; and    -   determine which data transformations are impacted if the type of        a specific database column is changed, say from VARCHAR to        INTEGER.

In a very general framework, in accordance with a preferred embodimentof the present invention, a binary relation such as “impacts” and itsinverse binary relation “is impacted by” are imposed on meta-classes.These relations model the dependencies whereby one class may impact ormay be impacted by another class, respectively. To generate these binaryrelations within a metamodel, appropriate meta-properties within themetamodel are characterized by “impacts” or “is impacted by”, and thebinary relations then correspond to the transitive closure of thesecharacterizations. Thus, if asset A impacts asset B, and asset B impactsasset C, then asset A also impacts asset C.

Within this general framework, the characterization of meta-propertiesas “impacts” or “is impacted by” is accomplished through a business rulereferred to as an “Inclusion BR” and a property referred to as“impacts”. The Inclusion BR indicates that a first property P1 isincluded in a second property P2, where the domain of P1 is a sub-classof the domain of P2; namely, that whenever instance I is related toinstance J via property P1, then instance I is also related to instanceI via property P2. It may be appreciated by those skilled in the artthat the Inclusion BR for P1 being included in P2 corresponds to P1being a sub-property of P2.

To make the property “impacts” as broad as possible, it is preferablydefined on a super-meta-class of the metamodel, such as a meta-class“Being” which is a super-meta-class of all meta-classes within themetamodel. Thus the Inclusion BR, indicating that a meta-property P froma domain meta-class C1 to a co-domain meta-class C2 is included inproperty “impacts”, requires that whenever instance I1 of meta-class C1is related to instance I2 of meta-class C2 via meta-property P, then I1impacts I2.

For example, for a meta-class “Server”, the Inclusion BR may specifythat the two meta-properties “hasRunningApplications”(Server-->Application) and “hasRunningDBs” (Server-->Database) areimpact meta-properties; i.e., included within the meta-property“impacts”. Thereafter an impact analysis on a specific server willproduce all applications that run on the server and all databases thatare hosted by the server. Similarly, for a meta-class “Application”, theInclusion BR may specify that the two meta-properties “is FeedingInto”(Application-->RDBTable) and “is CreatingXML”(Application-->XMLDocument) are impact properties. Combining these bytransitivity, a specific server may impact various relational databasetables and various XML documents.

More specifically, as there are various type of impacts in anenterprise, a variety of different impact analyses may be performed; forexample, a “downtime” impact analysis, a “procurement” impact analysis,or a “personnel” impact analysis. The same meta-class may participate inmultiple impact analyses. Reference is now made to FIG. 8, which is anillustration of a dialogue box for creating an impact analysis (IA)meta-class, in accordance with a preferred embodiment of the presentinvention. As shown in FIG. 8, a meta-class named “DowntimeImpactItem”810 is created, together with meta-properties “directDowntimeVictims”820 and “allDowntimeVictims” 830, the former property corresponding todirect dependencies and the latter property corresponding to both directand indirect dependencies. Also shown in FIG. 8 is the name of an impactanalysis, “Downtime Impact Analysis” 840, which is used to perform animpact analysis vis a vis downtime impacts.

The meta-class “DowntimeImpactItem” serves as a superclass for allmeta-classes whose instances can participate in the analysis. Thus, forexample, if ComputingDevice is a meta-class that should participate indowntime impact analysis, then it should be designated as a sub-class ofDowntimeImpactItem and, as such, it inherits the propertiesdirectDowntimeVictims and allDowntimeVictims. Instances of sub-classesof meta-class ComputingDevice, such as instances of a classServerComputer, of a class GatewayComputer and of a classClientComputer, will then all participate in downtime impact analysis.Any meta-class that inherits from DowntimeImpactItem can be includedwithin a downtime impact analysis. Similarly, if a meta-class inheritsfrom multiple meta-classes, each super-class being a specific impactanalysis type, then instances of the meta-class participate in each ofthe specific impact analyses.

It may thus be appreciated that an IA type of entity is preferablyrepresented by a meta-class that has a property such as inter alia“impacts”, “affects” or “hasConsequencesFor”. The name of the meta-classpreferably reflects the role of an instance class of its IA type, suchas inter alia “DownTimeImpactItem” or “ProcurementImpactItem”.

Reference is now made to FIG. 9, which is an illustration of a dialoguebox that continues the workflow from FIG. 8, for designating propertiesas being germane to a particular impact analysis, in accordance with apreferred embodiment of the present invention. Shown in the left panelof FIG. 9 is a meta-class “DowntimeImpactItem” 905, as defined in thedialogue box of FIG. 8, from which meta-classes “Application” 910 and“Server” 915 inherit, by virtue of being sub-classes thereof. Shown inthe right panel of FIG. 9 are various properties of the meta-classServer, such as “ApplicationID” 920, “Applications” 925, “CPU” 930 andthe inherited property directDowntimeVictims 935, as also defined in thedialogue box of FIG. 8. Also shown in FIG. 8 is a business rule thatassigns the meta-property “Applications” 940 to Downtime Impact Analysis945. For convenience, a user merely selects the Applicationsmeta-property 925 from the list of Server meta-properties, and thenclicks on the Add button 950. Such a business rule indicates thatinstance classes of Applications are impacted when correspondinginstance classes of Server go down. As such, when a downtime impactanalysis is performed, applications running on server computers will beincluded in the analysis. It may thus be appreciated by those skilled inthe art that impact analyses are conveniently defined via business rulesof a meta-model.

In accordance with a preferred embodiment of the present invention, inorder to simplify the workflow of defining impact analyses and in orderto avoid potential errors in the metamodel, when a user adds ameta-property, such as Applications, with meta-classes C1 and C2 as itsdomain and co-domain, respectively, to an impact analysis, thenmeta-classes C1 and C2 are automatically designated as sub-classes ofthe appropriate IA meta-class, such as DowntimeImpactItem. As such, auser does not have to set these sub-class designations manually. It isalso noted in FIG. 9 that, for convenience of implementation andmanagement, IA meta-classes are direct sub-classes of meta-class“Analyzable” 955.

Reference is now made to FIG. 10, which is an illustration of stepwisegraphical navigation of a meta-model, in accordance with a preferredembodiment of the present invention. The screen shown in FIG. 10 enablesa user to explore each node in a metamodel in a controlled way. Byclicking on a “plus” sign for a node A, a user instructs the navigatorto display all nodes that node A has an impact relation therewith,together with arrows that are labeled in accordance with the underlyingmeta-properties.

Shown in FIG. 10 is a computer server 1010 which runs applications 1020and 1030, and hosts a web site 1040. In turn, application 1020 writes toa data source 1050 and application 1030 writes to a data source 1060.Further in turn, data source 1050 is used by web sites 1070 and 1080,and data source 1060 is used in transformation 1090. All of theindicated properties are preferably included within an “impacts”property and, as such, server 1010 directly impacts the three IT assets1020, 1030 and 1040, and indirectly impacts the five IT assets 1050,1060, 1070, 1080 and 1090. It may thus be appreciated that using thepresent invention, an IT administrator is able to determine the impactof shutting down server 1010 or application 1020, for example.

In contrast to the stepwise navigation illustrated in FIG. 10, referenceis now made to FIG. 11, which is an illustration of a graphic display ofthe transitive closure of impacted nodes, in accordance with a preferredembodiment of the present invention. Shown in FIG. 11 is a list ofclasses impacted by a class “Cordoba15” 1105, which is an instance of ameta-class “Computer”. The list includes a class “Market Report” 1110and a class “Market Watch (Premium)” 1115, which are instances of ameta-class “Web Site” 1120, a class “WebSphere Business IntegrationEvent Broker 5.0” 1125 and a class “Active Reference” 1130 which areinstances of a meta-class “Application Version” 1135, a class “FRX-SAKO”1140 and a class “Market Stage” 1145, which are instances of ameta-class “Data Source” 1150, and a class “PBDEC to AMCS” 1155, whichis an instance of a meta-class “Transformation” 1160. The list includesclasses that are directly and indirectly impacted by Cordoba15.

When a user clicks on a specific item in the list, the chain of impactdependencies is displayed below. For example, the graphic display inFIG. 11 shows the dependency chain 1165 from Cordoba15 to Market Watch(Premium). Each of the arrows 1170, 1175 and 1180 correspond to a directimpact dependency.

It may be appreciated by those skilled in the art that, alternatively,binary relations “impacts” and “is impacted by” may correspond torelations other than the transitive closure of “impacts” and “isimpacted by” characterizations. For example, they may correspond to atransitive closure up to a specified number of levels, so that indirectimpact is restricted to, say, three levels.

It may also be appreciated that property inclusion may alternatively beimplemented using descriptors to tag certain meta-properties as beingimpact-related. However, implementation using an Inclusion BR allowsmore generality, including (i) allowing different types of impact or bedistinguished, and (ii) allowing inference to take advantage of the“impacts” property.

Data Lineage

A somewhat similar application to impact analysis is data lineage, whichis a technique for finding sources of property values. For example, auser may want to know “for a property “productName”, which is part of anEntity “Product Parameters”, which is part of a Data Asset“ProductSearchUI” where does its value come from?”

In accordance with a preferred embodiment of the present invention, datalineage is described as if it were a four-way impact analysis, using twoaxes. A first axis, the “data flow axis”, indicates the flow of datausing a property “Downstream Items” and a corresponding inverse property“Upstream Items”. A second axis, the “system composition axis”,indicates system components using a property “subUnits” and acorresponding inverse property “superUnits.” Reference is now made toFIG. 12, which is an illustration of a graphical user interface forviewing data lineage results arranged along the two above axes, inaccordance with a preferred embodiment of the present invention. Theresults illustrated in FIG. 12 are evoked when a user selects theproductName property and invokes data lineage analysis. The horizontalarrows depict the data flow axis and the vertical arrows depict thesystem composition axis.

Specifically, as seen in FIG. 12 from the vertical dependencies,“productName” 1210 is an attribute of a GenericEntity “ProductParameters” 1230, and Product Parameters 1230 is an asset from aDataAsset “ProductSearchUI” 1230. Moreover, as seen from the horizontaldependencies, productName 1210 is assigned a value based on acorresponding property “productName” 1240 of class “WsdlValuePart”. Inturn, productName 1240 is part of a message “product Search Response”1250. Moreover, productName 1240 is assigned a value from a Column“longName” 1260 of a relational database table “prod” 1270.

Reference is now made to FIG. 13, which is an illustration of agraphical user interface for marking meta-properties as being DownstreamItems, Upstream Items, subunits or superUnits, in accordance with apreferred embodiment of the present invention. As shown in FIG. 13, ameta-property “copiedFrom” 1310, is designated as being included inUpstream Items 1320, and its inverse meta-property, “copiedTo” 1330 isincluded in Downstream Items 1340. Specifically, “copiedFrom” and“copiedTo” are meta-properties from meta-class WsdlValuePart tometa-class ValueElement.

In the foregoing specification, the invention has been described withreference to specific exemplary embodiments thereof. It will, however,be evident that various modifications and changes may be made to thespecific exemplary embodiments without departing from the broader spiritand scope of the invention as set forth in the appended claims.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

1. A metadata management system for importing, integrating andfederating metadata, comprising: a configurable metamodel for modelingmetadata that describes enterprise IT assets; a metadata repository forstoring metadata whose structure reflects said metamodel; at least oneexternal metadata source, which is able to persist metadata inaccordance with the structure of a meta-schema; a mapping module formapping said meta-schema to the metamodel; and a transformation module,operatively coupled to said metadata mapping module, for translatingspecific metadata from said at least one external metadata source tosaid metadata repository, for use in import, export or synchronizationof metadata between said at least one external metadata source and saidmetadata repository.
 2. The metadata management system of claim 1wherein the mapping module is also used to map specific metadata to aninformation model.
 3. The metadata management system of claim 2 whereinthe information model is an ontology model.
 4. The metadata managementsystem of claim 1 wherein said metamodel complies with the OMG MOFstandard.
 5. The metadata management system of claim 1 wherein saidmetamodel is an ontology.
 6. The metadata management system of claim 1wherein said transformation module translates metadata from the externalmetadata source into an XMI document.
 7. The metadata management systemof claim 1 wherein said transformation module transforms metadata usingan XSLT script.
 8. The metadata management system of claim 1 whereinsaid mapping module maps data element groups, and then maps specificdata elements within each group.
 9. A metadata management system forvalidating metadata, comprising: a configurable metamodel for modelingmetadata that describes enterprise IT assets; business rules on saidmetamodel; and a metadata validation module operating on saidconfigurable metamodel for validating specific metadata against saidmetamodel business rules.
 10. The metadata management system of claim 9wherein the business rules include an arithmetic conversion rule. 11.The metadata management system of claim 9 wherein the business rulesinclude type restriction on an inherited property.
 12. The metadatamanagement system of claim 9 wherein the business rules includespecifying a metadata value as being required.
 13. The metadatamanagement system of claim 9 wherein the business rules includespecifying a valid range for a metadata value.
 14. The metadatamanagement system of claim 9 wherein the business rules includespecifying a metadata value as being unique.
 15. The metadata managementsystem of claim 9 wherein the business rules include a lookup table. 16.The metadata management system of claim 9 wherein the business rulesinclude a naming convention.
 17. The metadata management system of claim9 wherein the business rules are used to specify assignment ofstewardship responsibility.
 18. A metadata management system forgenerating metadata comprising: a configurable metamodel for modelingmetadata that describes enterprise IT assets; business rules on saidmetamodel; and a metadata generation module operating on saidconfigurable metamodel for guiding the generation of specific metadatausing said metamodel business rules.
 19. The metadata management systemof claim 18 wherein the business rules include an arithmetic conversionrule.
 20. The metadata management system of claim 18 wherein thebusiness rules include type restriction on an inherited property. 21.The metadata management system of claim 18 wherein the business rulesinclude specifying a metadata value as being required.
 22. The metadatamanagement system of claim 18 wherein the business rules includespecifying a valid range for a metadata value.
 23. The metadatamanagement system of claim 18 wherein the business rules includespecifying a metadata value as being unique.
 24. The metadata managementsystem of claim 18 wherein the business rules include a lookup table.25. The metadata management system of claim 18 wherein the businessrules include a naming convention.
 26. The metadata management system ofclaim 18 wherein the business rules are used to specify assignment ofstewardship responsibility.
 27. A metadata management system formanaging an IT organization, comprising: a configurable metamodel formodeling metadata that describes enterprise IT assets; business rules onsaid metamodel; and a validation module operating on said configurablemetamodel for validating rules for IT governance against said metamodelbusiness rules.
 28. The metadata management system of claim 27 whereinthe rules for IT governance include assignment of responsibility forassets.
 29. A method for importing, integrating and federating metadata,comprising: providing (i) a configurable metamodel for modeling metadatathat describes enterprise IT assets, (ii) a metadata repository forstoring metadata whose structure reflects the metamodel, and (iii) atleast one external metadata source, which is able to persist metadata inaccordance with the structure of a meta-schema; mapping the meta-schemato the metamodel; and translating specific metadata from the externalmetadata source to the metadata repository for use in import, export orsynchronization of metadata between the at least one external metadatasource and the metadata repository.
 30. The method of claim 29 whereinsaid mapping maps specific metadata to an information model.
 31. Themethod of claim 30 wherein the information model is an ontology model.32. The method of claim 29 wherein the metamodel complies with the OMGMOF standard.
 33. The method of claim 29 wherein the metamodel is anontology.
 34. The method of claim 29 wherein said mapping translatesmetadata from the external metadata source into an XMI document.
 35. Themethod of claim 29 wherein said translating uses an XSLT script.
 36. Themethod of claim 29 wherein said mapping comprises: mapping data elementgroups; and mapping specific data elements within each group.
 37. Amethod for validating metadata, comprising: providing (i) a configurablemetamodel for modeling metadata that describes enterprise IT assets, and(ii) business rules on the metamodel; and validating specific metadataagainst the metamodel business rules.
 38. A method for generatingmetadata comprising: providing (i) a configurable metamodel for modelingmetadata that describes enterprise IT assets, and (ii) business rules onthe metamodel; and guiding the generation of specific metadata using themetamodel business rules.
 39. A method for managing an IT organization,comprising: providing (i) a configurable metamodel for modeling metadatathat describes enterprise IT assets, and (ii) business rules on themetamodel; and validating rules for IT governance against the metamodelbusiness rules.
 40. The method of claim 29 wherein the rules for ITgovernance include assignment of responsibility for assets.
 41. Acomputer-readable storage medium storing program code for causing acomputer to perform a method of: providing (i) a configurable metamodelfor modeling metadata that describes enterprise IT assets, (ii) ametadata repository for storing metadata whose structure reflects themetamodel, and (iii) at least one external metadata source, which isable to persist metadata in accordance with the structure of ameta-schema; mapping the meta-schema to the metamodel; and translatingspecific metadata from the external metadata source to the metadatarepository for use in import, export or synchronization of metadatabetween the at least one external metadata source and the metadatarepository.
 42. A computer-readable storage medium storing program codefor causing a computer to perform a method of: providing (i) aconfigurable metamodel for modeling metadata that describes enterpriseIT assets, and (ii) business rules on the metamodel; and validatingspecific metadata against the metamodel business rules.
 43. Acomputer-readable storage medium storing program code for causing acomputer to perform a method of: providing (i) a configurable metamodelfor modeling metadata that describes enterprise IT assets, and (ii)business rules on the metamodel; and guiding the generation of specificmetadata using the metamodel business rules.
 44. A computer-readablestorage medium storing program code for causing a computer to perform amethod of: providing (i) a configurable metamodel for modeling metadatathat describes enterprise IT assets, and (ii) business rules on themetamodel; and validating responsibility assignments against themetamodel business rules.
 45. A metadata management system forperforming impact analysis on an IT system comprising: a configurablemetamodel for modeling metadata that describes assets of an enterpriseIT system, the metamodel including meta-classes and meta-properties;business rules on said metamodel for indicating that certainmeta-properties have impact consequences; and an impact analyzeroperating on said configurable metamodel for determining which assets ofthe enterprise IT system are impacted by one or more specified assets.46. The metadata management system of claim 43 whereby assets of theenterprise IT system include server computers.
 47. The metadatamanagement system of claim 43 whereby assets of the enterprise IT systeminclude web sites.
 48. The metadata management system of claim 43whereby assets of the enterprise IT system include data sources.
 49. Themetadata management system of claim 43 whereby assets of the enterpriseIT system include data transformations.
 50. The metadata managementsystem of claim 43 whereby assets of the enterprise IT system includesoftware applications.
 51. The metadata management system of claim 43whereby the business rules dictate whether impact consequences aretransitive and, if so, to what degree.
 52. A method for generatingmetadata comprising: providing (i) a configurable metamodel for modelingmetadata that describes assets of an enterprise IT system, the metamodelincluding meta-classes and meta-properties, and (ii) business rules onsaid metamodel for indicating that certain meta-properties have impactconsequences; and determining which assets of the enterprise IT systemare impacted by one or more specified assets.
 53. The method of claim 52whereby assets of the enterprise IT system include server computers. 54.The method of claim 52 whereby assets of the enterprise IT systeminclude web sites.
 55. The method of claim 52 whereby assets of theenterprise IT system include data sources.
 56. The method of claim 52whereby assets of the enterprise IT system include data transformations.57. The method of claim 52 whereby assets of the enterprise IT systeminclude software applications.
 58. The method of claim 52 whereby thebusiness rules dictate whether impact consequences are transitive and,if so, to what degree.
 59. A computer-readable storage medium storingprogram code for causing a computer to perform a method of: providing(i) a configurable metamodel for modeling metadata that describes assetsof an enterprise IT system, the metamodel including meta-classes andmeta-properties, and (ii) business rules on said metamodel forindicating that certain meta-properties have impact consequences; anddetermining which assets of the enterprise IT system are impacted by oneor more specified assets.
 60. A metadata management system forperforming impact analysis on an IT system comprising: a configurablemetamodel for modeling metadata that describes assets of an enterpriseIT system, the metamodel including meta-classes and meta-properties; ameta-descriptor for meta-properties to designate that a meta-propertyhas an impact consequence; and an impact analyzer operating on saidconfigurable metamodel for determining which assets of the enterprise ITsystem are impacted by one or more specified assets.
 61. A method forgenerating metadata comprising: providing (i) a configurable metamodelfor modeling metadata that describes assets of an enterprise IT system,the metamodel including meta-classes and meta-properties, and (ii) ameta-descriptor for meta-properties to designate that a meta-propertyhas an impact consequence; and determining which assets of theenterprise IT system are impacted by one or more specified assets.
 62. Acomputer-readable storage medium storing program code for causing acomputer to perform a method of: providing (i) a configurable metamodelfor modeling metadata that describes assets of an enterprise IT system,the metamodel including meta-classes and meta-properties, and (ii) ameta-descriptor for meta-properties to designate that a meta-propertyhas an impact consequence; and determining which assets of theenterprise IT system are impacted by one or more specified assets.